Memory leakage when loading/closing multiple modules

Here is what I'm seeing. Can someone explain to me why there is a memory usage difference between the 2 methods of loading and closing modules?

I start DOORS and in my Task Manager it shows doors.exe uses 82,784k memory.

Method 1:

1. Opened module A (baseline current)

2. Closed module A (baseline current)

3. Opened module A (baseline 1.0)

4. Closed module A (baseline 1.0)

In Task Manager, it shows doors.exe uses 85,728k

I then restarted DOORS.

In Task Manager it shows doors.exe uses 82,685k memory (close to what I started with in method 1)

Method 2:

1. Opened module A (baseline current)

2. Opened module A (baseline 1.0)

3. Closed module A (baseline current)

4. Closed module A (baseline 1.0)

In Task Manager, it shows doors.exe uses 276,580k

276,580k is not even close to what I've started with. So why is there a difference depending on the order of how the modules were opened and closed?

Thanks,

Re: Memory leakage when loading/closing multiple modules
GothSloth - Mon Sep 16 13:19:13 EDT 2013

After each method try "Tools->Manage Open Modules" to see if any modules were opened in the background and are still open.

Re: Memory leakage when loading/closing multiple modules
Anaheim - Mon Sep 16 14:38:02 EDT 2013

I did check and nothing is displayed in there for both steps. This is why it's puzzling me.